Skip to content

docs(lstk hotfix): update CLI reference to v0.22.0 - #850

Open
gtsiolis wants to merge 3 commits into
mainfrom
claude/affectionate-edison-3sg384
Open

docs(lstk hotfix): update CLI reference to v0.22.0#850
gtsiolis wants to merge 3 commits into
mainfrom
claude/affectionate-edison-3sg384

Conversation

@gtsiolis

@gtsiolis gtsiolis commented Aug 6, 2026

Copy link
Copy Markdown
Member

Brings the lstk CLI reference docs up to date with the v0.22.0 release of localstack/lstk, catching up the full backlog from the last-documented v0.19.0. This PR started as the v0.21.0 sync; it now also folds in the v0.21.0 → v0.22.0 delta, so it covers the whole v0.19.0 → v0.22.0 range (v0.20.0, v0.20.1, v0.21.0, and v0.22.0) verified against the CLI at the v0.22.0 tag. main was merged in so the diff is a clean superset of the current docs.

Reference pages in scope

  • src/content/docs/aws/developer-tools/running-localstack/lstk.mdx
  • src/content/docs/azure/developer-tools/lstk.mdx

There are no shared lstk components yet, so each page carries its own reference content and both are kept in sync.

What changed

v0.21.0 → v0.22.0 (new in this update)

expose_ports config option (localstack/lstk#433) — added to the default config.toml snippet and the config field reference table on both pages. Documents the grammar (a bare port, or a Docker-style "[host:]container[/proto]" string; an entry with no protocol publishes both TCP and UDP) with the DNS-server ([53]) and "5354:5353/udp" examples. This is the config surface previously tracked in DOC-392; that change never landed in main, so it is consolidated here.

lstk aws --account (localstack/lstk#440) — the aws proxy now accepts a leading --account <12 digits> flag (default 000000000000, falling back to the ambient AWS_ACCESS_KEY_ID), matching the flag lstk terraform and lstk sam already expose. Added an options-table row, an example, and a short note that lstk cdk deliberately has no --account.

Not documented (verified out of scope for these two reference pages): the extension-context additions endpointUrl/machineId (localstack/lstk#446) live in the extension-authoring contract, not the CLI reference; the lstk start invisible-re-login fix (localstack/lstk#449) only fixes behavior the Offline/enterprise section already describes; telemetry exit-code recording (localstack/lstk#396) is internal.

v0.19.0 → v0.21.0 (carried from the earlier sync)

Review

Advisable. Most edits are mechanical reference updates, but a couple touch user-facing wording worth a glance: the reversed auth-token precedence (a behavior change users may have scripted around) and the "Port 443" drop-with-warning framing.

Closes DOC-393

Cc @localstack/devx for visibility and any corrections.

Co-Authored-By: Claude <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 6, 2026

Copy link
Copy Markdown

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: ea16d19
Status: ✅  Deploy successful!
Preview URL: https://cc88fcd3.localstack-docs.pages.dev
Branch Preview URL: https://claude-affectionate-edison-3.localstack-docs.pages.dev

View logs

gtsiolis commented Aug 6, 2026

Copy link
Copy Markdown
Member Author

The Validate Refs check is expected to be red here. That job only passes when the head branch is named aws-docs-*/snowflake-docs-*, and this is the release-independent lstk hotfix flow (a claude/* branch into main), the same setup as the previous lstk reference hotfixes (#830, #833, #788).

Please don't retarget the base to make it green — retargeting mid-merge is what sent #774 to the wrong branch. Merge via the usual hotfix path. Cloudflare Pages (the check that actually builds the docs) passed.


Generated by Claude Code

@gtsiolis gtsiolis changed the title docs(lstk hotfix): update CLI reference to v0.21.0 docs(lstk hotfix): update CLI reference to v0.22.0 Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants